Devices, methods, and systems for multi-user commissioning

ABSTRACT

Devices, methods, and systems for multi-user commissioning are described herein. One system includes a mobile computing device comprising computer readable instructions stored thereon that are executable by a processor to: retrieve configuration data for a physical controller from a remote database, install the configuration data on the physical controller, receive data associated with a status of the physical controller after the configuration data is installed on the physical controller, and synchronize the data associated with the status of the physical controller with the remote database.

TECHNICAL FIELD

The present disclosure relates to devices, methods, and systems formulti-user commissioning.

BACKGROUND

A database can be utilized to store data for a particular project. Forexample, the database can be utilized to store data relating theprogress or completion of the particular project. In addition, thedatabase can be utilized to store information that can be utilized bytechnicians or other users that are attempting to complete theparticular project. For example, the database can be utilized to storeschematics and other technical information for completing the particularproject. In some examples it can be difficult to maintain real time datawith the database. For example, the stored information may be limited toa single user access and update.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is an example of a system for multi-user commissioning accordingto one or more embodiments of the present disclosure.

FIG. 2 is an example of a display for multi-user commissioning accordingto one or more embodiments of the present disclosure.

FIG. 3A is an example of displays for multi-user commissioning accordingto one or more embodiments of the present disclosure.

FIG. 3B is an example of displays for multi-user commissioning accordingto one or more embodiments of the present disclosure.

FIG. 3C is an example of displays for multi-user commissioning accordingto one or more embodiments of the present disclosure.

FIG. 4 is an example of a method for multi-user commissioning accordingto one or more embodiments of the present disclosure.

FIG. 5 is an example of a method for multi-user commissioning accordingto one or more embodiments of the present disclosure.

FIG. 6 is an example of a computing device for multi-user commissioningaccording to one or more embodiments of the present disclosure.

DETAILED DESCRIPTION

Devices, methods, and systems for multi-user commissioning are describedherein. One system includes a mobile computing device comprisingcomputer readable instructions stored thereon that are executable by aprocessor to: retrieve configuration data for a physical controller froma remote database, install the configuration data on the physicalcontroller, receive data associated with a status of the physicalcontroller after the configuration data is installed on the physicalcontroller, and synchronize the data associated with the status of thephysical controller with the remote database.

In another example, a mobile computing device can include instructionsto: download project instructions for a project from a remotedistributed database, generate a project checklist for the project basedon the project instructions and information scanned from a deviceassociated with the project, receive selectable inputs corresponding tothe project checklist, and synchronize inputs for the project checklistwith the remote distributed database.

Devices, methods, and systems for multi-user commissioning describedherein can utilize a distributed database to provide two way datacommunication between the distributed database and a plurality of mobilecomputing devices. In some examples, the mobile computing devices canupdate an application on the mobile computing device via the two waydata communication. In some examples, the mobile computing device canupdate data relating to a project (e.g., construction project, etc.) viathe application on the mobile computing device. In some examples, thedata relating to the project can be synchronized with project datawithin the distributed database.

In some examples, the mobile computing device can download dataassociated with the project. In some examples, the data associated withthe project can include configuration data. In some examples, theconfiguration data configures a number of settings for functionality ofthe physical controller upon being installed on the physical controller.For example, the mobile computing device can download binary files toconfigure a physical controller by uploading the binary files to thephysical controller. In this example, the mobile computing device candownload the configuration data from the distributed database andinstall the configuration data on the physical controller.

In some examples, the mobile computing device can request configurationdata based on information scanned from a physical controller. Forexample, a user can scan a code located on the physical controller orbox of the physical controller. In this example, the mobile computingdevice can request the configuration data for the physical controllerbased on the scan of the code.

In some examples, the mobile computing device can be utilized to displaya project checklist based on project information stored at thedistributed database. In some examples, the project checklist caninclude a number of selectable inputs. In some examples, the number ofselectable inputs can correspond to a number of project tasks that auser may complete prior to completing the project. For example, thenumber of project tasks can include a wiring checkout, a sensorcalibration, and/or a sequence validation of test results, among otherproject tasks that are associated with the project.

Devices, methods, and systems for multi-user commissioning describedherein can be utilized to enable a plurality of users to performcommissioning activities for the project. For example, a plurality ofusers can each utilize a mobile computing device that can be utilized todownload project information and synchronize data associated with thestatus of physical controllers and/or project checklists with thedistributed database.

In the following detailed description, reference is made to theaccompanying drawings that form a part hereof. The drawings show by wayof illustration how one or more embodiments of the disclosure may bepracticed.

These embodiments are described in sufficient detail to enable those ofordinary skill in the art to practice one or more embodiments of thisdisclosure. It is to be understood that other embodiments may beutilized and that process changes may be made without departing from thescope of the present disclosure.

As will be appreciated, elements shown in the various embodiments hereincan be added, exchanged, combined, and/or eliminated so as to provide anumber of additional embodiments of the present disclosure. Theproportion and the relative scale of the elements provided in thefigures are intended to illustrate the embodiments of the presentdisclosure, and should not be taken in a limiting sense.

The figures herein follow a numbering convention in which the firstdigit or digits correspond to the drawing figure number and theremaining digits identify an element or component in the drawing.Similar elements or components between different figures may beidentified by the use of similar digits.

FIG. 1 is an example of a system 102 for multi-user commissioningaccording to one or more embodiments of the present disclosure. Thesystem 102 can utilize a network 110 to allow a plurality of users104-1, 104-2, 104-3, 104-4 with mobile computing devices 106-1, 106-2,106-3, 106-4 to communicate with a distributed database. In someexamples, the mobile computing devices 106-1, 106-2, 106-3, 106-4 cansimultaneously communicate with the distributed database viacommunication paths 108-1, 108-2, 108-3, 108-4.

In some examples, the network 110 can be a cloud network that is coupledto the distributed database. As described herein, the plurality of users104-1, 104-2, 104-3, 104-4 can utilize the mobile computing devices106-1, 106-2, 106-3, 106-4 to: retrieve configuration data for aphysical controller from the distributed database, install theconfiguration data on the physical controller, receive data associatedwith a status of the physical controller after the configuration data isinstalled on the physical controller, synchronize the data associatedwith the status of the physical controller with the remote database,among other functions to help the plurality of users 104-1, 104-2,104-3, 104-4 complete the project and/or update a status of the project.In some examples, data associated with a status of the physicalcontroller includes installation instructions for the physicalcontroller and checkout instructions for the physical controller. Thesystem 102 can allow the plurality of users 104-1, 104-2, 104-3, 104-4access data relating to the project via the mobile computing devices106-1, 106-2, 106-3, 106-4 and update the distributed database with acompleted tasks relating to the project by synchronizing the mobilecomputing devices 106-1, 106-2, 106-3, 106-4 with the distributeddatabase via the network 110.

In some examples, the system 102 can allow the plurality of users 104-1,104-2, 104-3, 104-4 to simultaneously update a status of the project. Insome examples, the project can include a plurality of sub-projectsand/or portions of the project. In some examples, a first user 104-1 candownload information for a first portion of the project and a seconduser 104-2 can download information for a second portion of the project.In this example, the first user 104-1 and the second user 104-2 cansynchronize the respective portion of the project simultaneously. Insome examples, it can be advantageous to have real time status of theproject to determine a timeline for completion of the project, determinewhen a different user can begin a project, and/or resources that may beneeded for completion of the project.

FIG. 2 is an example of a display 206 for multi-user commissioningaccording to one or more embodiments of the present disclosure. In someexamples, the display 206 can be displayed on a user interface of amobile computing device (e.g., mobile computing device 106-1, 106-2,106-3, 106-4 as referenced in FIG. 1, etc.). In some examples, thedisplay 206 can be utilized to retrieve data (e.g., schematics,configuration data, etc.) relating to the project and/or updating astatus of the project, and/or displaying a status of the project.

In some examples, the display 206 can include a header 220. In someexamples, the header 220 can display a description of information beingdisplayed on the display 206. For example, the header 220 can displayoverview when the display 206 is utilized to display a general overviewof status information relating to the project. In another example, theheader 220 can display a name of a physical controller or project namewhen the display is utilized to display project information relating toinstalling the physical controller.

Display 206 can display the general overview of status informationrelating to the project. For example, the display can include controllerstatus 218. In some examples, the controller status 218 can includestatus information relating to the installation and configuration of anumber of physical controllers. For example, the controller status 218can include a total quantity of physical controllers relating to aproject, a quantity of plant controllers, and/or a quantity of unitarycontrollers.

In some examples, the display 206 can include a status indicator 212. Insome examples, the status indicator 212 can include a graphicalrepresentation that indicates a percentage of completion for a selectedproject or category. For example, the header 220 can be utilized toselect a particular project, portion of a project, and/or a particulardevice of a particular project. In this example, the status indicator212 can indicate a percentage of completion for the particular project,portion of a project, and/or the particular device of a particularproject. In some examples, the header 220 can be utilized to select aparticular category. For example, the header 220 can be utilized toselect between an installation check category, a wiring check category,a point check category, and a functional check category.

In some examples, the installation check category can include a status,inputs, installation diagrams, installation information, and/orselections related to an installation of a particular device. In someexamples, the wiring check category can include status, inputs, wiringdiagrams, wiring information, and/or selections related to wiring theparticular device. In some examples, the point check category caninclude status, inputs, diagrams for point tests, point testinformation, and/or selections relating to performing a point test ofthe particular device. In some examples, the functional check categorycan include a status, inputs for performing the functional check asdescribed herein, diagrams for performing the functional check, and/orselections relating to performing the functional check. As describedherein, the display 206 can be utilized to track and manage the numberof categories.

In some examples, the status indicator 212 can be updated uponcompletion of a project checklist. For example, the status indicator 212can be updated to reflect a greater percentage of completion when aproject is complete and/or when a portion of the project checklist hasbeen complete. As described herein, the mobile computing device utilizedfor the display 206 can retrieve data from the distributed database. Insome examples, the retrieved data can be utilized to update the statusindicator 212. In addition, the mobile computing device can synchronizecompletion data with the distributed database. By retrieving data andsynchronizing completion data, the mobile computing device can utilizethe display 206 for displaying the status indicator 212 with real timedata. In addition, the distributed database can be accessed by aplurality of additional devices to monitor the completion status of theproject.

In some examples, the display 206 can include a test indicator 214. Insome examples, the test indicator 214 can include a status of testingperformed on physical controllers. As described further herein, a usercan input test results into the mobile computing device. The testresults that are input into the mobile computing device can be utilizedto determine when a test has passed, failed, or was unable to test. Insome examples, the test indicator 214 can be synchronized with thedistributed database. For example, the test indicator 214 can be updatedbased on data retrieved from the distributed databased. In anotherexample, the test results that are input into the mobile computingdevice can be uploaded to the distributed database. In some examples,the display 206 can be utilized to record a number of tests on thephysical controller and synchronize results from the number of testswith the distributed database (e.g., remote distributed database, etc.).

In some examples, the display 206 can include a number of selectablefunctions 216. In some examples, the selectable functions 216 caninclude, but are not limited to: an overview function, an installfunction, a point shortcut function, and/or a function shortcutfunction. In some examples, the selectable functions 216 can be selectedby a user to perform a number of functions described herein. Forexample, the selectable functions 216 can include an install function toinstall configuration data on to a physical controller. In someexamples, the configuration data can be retrieved from the distributeddatabase by the mobile computing device. In some examples, the retrievedconfiguration data can be utilized to configure the physical controller.

As described herein, the display 206 can be utilized by a user of themobile computing device to view project status information, perform anumber of tests, update a checklist corresponding to the project, and/orretrieve/install configuration data.

FIG. 3A is an example of displays 330-1 for multi-user commissioningaccording to one or more embodiments of the present disclosure. In someexamples, the displays 330-1 can be displayed on a user interface of amobile computing device as described herein. In some examples, thedisplays 330-1 can be similar to display 206 as referenced in FIG. 2.

In some examples, the displays 330-1 can include a header 320-1, 320-2.In some examples, the header 320-1, 320-2 can display a project and/ordevice (e.g., physical controller). In some examples, the header 320-1,320-2 can be utilized to select a particular project and/or portion of aproject. For example, a user can utilize the header 320-1, 320-2 toselect a project, portion of the project, and/or a particular device tobe installed as part of the project. As described herein, selecting aparticular project, portion of the project, and/or particular device candisplay information relating to the selected project, portion of theproject, and/or particular device.

In one example, the header 320-1, 320-2 includes a particular device(e.g., VAV box, physical controller, etc.). When a particular device isselected, information 332-1, 332-2 corresponding to the particulardevice can be displayed. In some examples, the information 332-1, 332-2can include, but is not limited to: a device name, a serial number, adevice type, a mode of the device, a status of the device, a state ofthe device, and/or a designated user or group of users responsible forthe device. As described herein, the information 332-1, 332-2 can beretrieved from the distributed database.

In some examples, the displays 330-1 can include a device test 334-1,334-2. In some examples, the device test 334-1, 334-2 can include apresent value and a record test value. In some examples, the presentvalue can be a value recorded by the selected device from the header320-1, 320-2. In some examples, the present value can be a valuerecorded by a physical controller coupled to the selected device fromthe header 320-1, 320-2. In some examples, a user can input a test valuefrom the site of the selected device from the header 320-1, 320-2. Thetest value can be a reading from a device other than the physicalcontroller to test the accuracy of the physical controller.

In some examples, the test value can be compared to the present value.In some examples, an offset can be selected based on a determination ofan acceptable range of values. For example, a determination can be madethat an acceptable range of the comparison consists when the presentvalue is within 3 units (e.g., +/−3 units, etc.) of the test value. Inanother example, the present value can be a temperature readingdetermined by a physical controller coupled to variable air volume (VAV)box and the test value can be a reading determined by a user at thelocation of the VAV box. In this example, the acceptable range can be adifference of plus or minus 3 degrees to ensure that readings from thephysical controller can be utilized to identify when a malfunction hasoccurred with the VAV box.

In some examples, a pass/fail input 336 can be utilized to select when aparticular controller has passed or failed based on whether the comparedvalue is within the acceptable range and/or offset. For example, whenthe compared value is within the acceptable range, pass can be selectedfrom the pass/fail input 336. In this example, selecting pass from thepass/fail input 336 can result in a pass indication 338 to be displayed.In some examples, the pass indication 338 can be synchronized with thedistributed database as described herein.

In some examples, the displays 330-1 can be utilized to automaticallycalculate and/or enter an offset value from a measured value. In someexamples, the displays 330-1 can be utilized to display a value from acontroller coupled to a device such that the displayed value can beautomatically calibrated to match a field measured value.

In some examples, the displays 330-1 can include a text input 340. Insome examples, the text input 340 can be utilized to add comments to thedata corresponding to the selected device displayed in the header 320-2.In some examples, the comments added via the text input 340 can besynchronized with the distributed database. Thus, the comments added viathe text input 340 can be accessed by a number of other users asdescribed herein. In some examples, the text input 340 can be used todescribe test conditions and/or other features unique to the selecteddevice.

In some examples, the displays 330-1 can include an image input 342. Theimage input 342 can be utilized to add images to the data correspondingto the selected device displayed in the header 320-2. In some examples,the images added via the image input 342 can be synchronized with thedistributed database. Thus, the images added via the image input 342 canbe accessed by a number of other users as described herein.

As described herein, the displays 330-1 can be displayed on a mobilecomputing device and enable a user of the mobile computing device toretrieve information relating to a project, portion of a project, and/ordevice. In addition, the displays 330-1 can be utilized to perform anumber of tests relating to the project and/or device. As describedherein, the information and/or data relating to the project can beupdated and synchronized with the distributed database.

FIG. 3B is an example of displays 330-2 for multi-user commissioningaccording to one or more embodiments of the present disclosure. In someexamples, the displays 330-2 can include similar selection items as thedisplays 330-1 referenced in FIG. 3A. In some examples, the displays330-2 can be displayed on a user interface of a mobile computing deviceas described herein. In some examples, the displays 330-2 can bedisplayed upon selection of a controller selection tab from the displays330-1 referenced in FIG. 3A.

In some examples, the displays 330-2 can be utilized to display afiltering of controllers within a building or area. In some examples,the displays 330-2 can be utilized to filter the controllers based on abuilding, facility, area, network layout of an area, a controller type,and/or a controller name. In some examples, the left display from thedisplays 330-2 can be utilized to select a particular controller fromthe filtered controllers. In response to selecting a particularcontroller from the left display can initiate the right display from thedisplays 330-2. In some examples, the right display can include asummary list of points for the selected controller. In some examples,the right display can be utilized to display current values for the listof points. In some examples, the right display can view current values,wiring checkout category information, and/or point checkout statusinformation as described herein.

In some examples, the displays 330-2 can include a header 320-3, 320-4to display a controller name or category of controllers. For example,the header 320-3 on the left display can include a selection for a typeof categorization of the controllers for an area or building. In someexamples, the header 320-3 can include the number of categoriesdescribed herein. For example, the header 320-3 can include a number ofselections corresponding to the number of categories and a list ofcontrollers 325 can be displayed based on the selection of thecorresponding category. For example, the header 320-3 can include a sitecategory, a network category, and/or a controller list category. In someexamples, the header 320-3 can include additional or fewer categories.

In some examples, a user can select a particular controller from thelist of controllers 325 and the right display can be displayed to theuser. In some examples, the right display can include a header 320-4 todisplay the controller selected by a user from the left display. In someexamples, the right display can include a filter selection 321 to filterthe value points for the selected controller. In some examples, theright display can include a list of points 323. In some examples, thelist of points 323 can include current values for each point, wiringcheckout status for each point, and/or point checkout status informationfor each point.

FIG. 3C is an example of displays 330-2 for multi-user commissioningaccording to one or more embodiments of the present disclosure. In someexamples, the displays 330-3 can include similar selection items as thedisplays 330-1 referenced in FIG. 3A. In some examples, the displays330-3 can be displayed on a user interface of a mobile computing deviceas described herein. In some examples, the displays 330-3 can bedisplayed upon selection of a controller selection tab from the displays330-1 referenced in FIG. 3A. In some examples, the left display can bethe same or similar display as the right display from FIG. 3B.

In some examples, the left display can include a header 320-5 to displaythe controller selected by a user from the left display. In someexamples, the left display can include a filter selection to filter thevalue points for the selected controller. In some examples, the leftdisplay can include a list of points 323. In some examples, the list ofpoints 323 can include current values for each point, wiring checkoutstatus for each point, and/or point checkout status information for eachpoint.

In some examples, the header 320-5 can include a filter selection 327.In some examples, the filter selection 327 can be selected to displaythe right display. In some examples, the right display can include anumber of filter options 329. The filter options 329 can include anumber of options for filtering displayed points on the left display. Insome examples, a user can select a point from the list of points 323 todisplay the displays 330-1 as referenced in FIG. 3A.

In some examples, the filter options 329 can include a plants selectionto select or display a particular area, building, or project. In someexamples, the filter options 329 can include a number of point typeselections to define a particular point type or point types to displayon the list of points 323. In some examples, the filter options 329 caninclude a wiring checkout status to display controllers with aparticular wiring checkout status on the list of points 323. In someexamples, the filter options 329 can include the point checkout statusto display controllers with a particular checkout status on the list ofpoints 323. In some examples, the filter options 329 can include a boardselection to display controllers with a particular system board. In someexamples, the selected filter options can be implemented on the list ofpoints 323 by selecting a done button 331.

FIG. 4 is an example of a method 450 for multi-user commissioningaccording to one or more embodiments of the present disclosure. In someexamples, the method 450 can be performed by a number of computingdevices as described herein. For example, a first computing device canexecute studio instructions 452-1, 452-2 and a second computing devicecan execute ICS APP instructions 454. In some examples, the secondcomputing device can be a mobile computing device that can execute theICS APP instructions 454 to perform a portion of the method 450.

In some examples, the method 450 can include creating a project instudio at 456-1. As used herein, studio is a user interface of acomputing device for inputting data relating to a number of projects.For example, a project can include an installation of a heating,ventilation, and air conditioning (HVAC) system. In this example, theproject can include data and information for completing the installationof the HVAC system. As described herein, the data and information caninclude schematics for installing devices associated with the HVACsystem, instructions for installing physical controllers, and/orconfiguration data for the physical controllers.

In some examples, the method 450 can include completing controllersengineering at 456-2. In some examples, completing controllersengineering can include identifying a location to install a plurality ofphysical controllers. In some examples, completing controllersengineering can include generating configuration data for a plurality ofphysical controllers.

In some examples, the method 450 can include synchronizing/exportingproject data at 456-3. As described herein, data corresponding to theproject can be synchronized with a distributed database such that aplurality of mobile computing devices can simultaneously display andupdate information corresponding to the project. In some examples, thedata can be exported to a plurality of mobile computing devices usingtwo-way communication. In some examples, a cloud network can be utilizedto synchronize the distributed database with a plurality of mobilecomputing devices.

In some examples, the method 450 can include downloading binaryconfiguration data at 456-4. In some examples, downloading binaryconfiguration data can include downloading instructions that can beinstalled on to a physical controller. In some examples, the binaryconfiguration data can configure a physical controller such that thecontroller functions under designated conditions.

In some examples, the method 450 can include launching the applicationon a mobile computing device at 458-1. Launching the application on amobile computing device can include opening ICS APP instructions 454 asdescribed herein. In some examples, the application can include a userinterface/display as described herein. For example, the application canbe utilized to display a status of the project, perform a number oftests, and/or synchronize data with the distributed database.

In some examples, the method 450 can include selecting a project and/ordownloading project information at 458-2. As described herein, theapplication on the mobile computing device can be utilized to select aproject via a header displayed via the application. In some examples,the application of the mobile computing device can download projectinformation such as project schematics, wiring instructions, and/orother information relating to completion of the project.

In some examples, the method 450 can include showing controller networkview at 458-3. In some examples, showing controller network view caninclude displaying a network view of a plurality of physical controllersrelated to a particular project. In some examples, the controllernetwork view can be based on information downloaded at 458-2.

In some examples, the method 450 can include selecting a DDC board at458-4. In some examples, selecting the DDC board can include selecting aparticular device as described herein. In some examples, selecting theDDC board can be based on a particular controller to be configured asdescribed herein.

In some examples, the method 450 can include downloading to controllerby ICS APP at 458-5. In some examples, the mobile computing device candownload the binary configuration data at the location of a particularcontroller to be configured. As described herein, the binaryconfiguration data can be installed on a physical controller forconfiguration of the controller.

In some examples, the method 450 can include setting an offset at 458-6.As described herein, the offset can be a quantity of units that acontroller reading can be different than a test performed. For example,the offset can be utilized to ensure that the physical controller iswithin a particular range of accuracy. In some examples, the offset canbe utilized to control a sensitivity and/or accuracy of the controllerreadings.

In some examples, the method 450 can include updating status of thecontroller at 458-7. In some examples, updating the status of thecontroller can include receiving a reading from the controller andcomparing the reading to a test value. In this example, the controllercan have a pass rating when the difference between the received readingand test value are within the offset. In this example, the controllercan have a fail rating when the difference between the received readingand the test value are outside the offset.

In some examples, the method 450 can include synchronizing the data at458-8. As described herein, synchronizing the data can includesynchronizing updated data from the mobile computing device with thedistributed database. In some examples, the data can include a pass/failrating, text data relating to the pass/fail rating, a number of imagesrelating to the pass/fail rating, and/or a confirmation that aparticular project or portion of the project has been completed.

In some examples, the method 450 can include generating a report instudio at 460. In some examples, generating the report in studio caninclude utilizing the data from the ICS APP 454 to generate a report ofthe progress on the project. In some examples, generating the report caninclude updating the distributed database. In some examples, updatingthe distributed database can include updating the project status on aplurality of mobile computing devices coupled to the distributeddatabase.

FIG. 5 is an example of a method 570 for multi-user commissioningaccording to one or more embodiments of the present disclosure. In someexamples, the method 570 can be executed by a computing device. Forexample, the method 570 can be executed by a mobile computing devicesuch as a smartphone or tablet.

At 572, the method 570 can include receiving, at a mobile computingdevice, a notification of a project associated with a physicalcontroller. In some examples, receiving the notification of the projectcan include a message received from a distributed database that a userof the mobile computing device is assigned a particular project. In someexamples, the project can include an installation or test of thephysical controller. In some examples, the notification can include adescription of the project and a location of the physical controller.

At 574, the method 570 can include downloading, at the mobile computingdevice, project instructions for the project from a remote distributeddatabase, wherein the project instructions includes configuration datafor the physical controller. As described herein, data relating to theproject can be downloaded by the mobile computing device. In someexamples, the data relating to the project can include projectinstructions (e.g., wiring diagrams, location of installation, etc.). Insome examples, the data relating to the project can includeconfiguration data that can be utilized for configuring the physicalcontroller. For example, the configuration data can include binaryconfiguration data that can be installed on the physical controller viathe mobile computing device.

At 576, the method 570 can include generating, at the mobile computingdevice, a project checklist for the project based on the projectinstructions for the project, wherein the project checklist includesinstructions to upload the configuration data to the physicalcontroller. In some examples, the project checklist can include tasks tocomplete for proper installation and testing of the physical controller.In some examples, the project checklist can include an option for aproject check out (e.g., tasks to complete before indicating the projectis complete). In some examples, the project checklist can include anumber of inputs for indicating that a particular task has beencomplete. In some examples, the project checklist can also include anumber of inputs for testing the physical controller as describedherein.

At 578, the method 570 can include updating, at the mobile computingdevice, the project checklist to include information relating tocompleted tasks associated with the project, wherein the completed tasksinclude uploading the configuration data to the physical controller. Insome examples, updating the project checklist can include receivinginputs, at the mobile computing device, to indicate test results and/orcompletion of particular tasks associated with the project.

At 580, the method 570 can include synchronizing, at the mobilecomputing device, the project checklist with the remote distributeddatabase. As described herein, the mobile computing device can beutilized to synchronize updated data with the remote distributeddatabase. For example, the project checklist can be completed and testscan be performed to confirm correct configuration of the physicalcontroller. In this example, the updated data can be synchronized withthe remote distributed database such that progress of the project can betracked.

In some examples, the method 570 can include displaying, on a display ofthe mobile computing device, the generated project checklist. Asdescribed herein, the project checklist can include a plurality of stepsor actions to be performed prior to completing the project. In someexamples, the project checklist can be displayed on the user interfaceof the mobile computing device such that a user can input selectionswhen the user has completed a particular step or action of the projectchecklist. For example, the method 570 can include receiving inputs, atthe display of the mobile computing device, corresponding to the projectchecklist upon completion of tasks associated with the project.

In some examples, the method 570 can include calibrating the physicalcontroller by uploading the configuration data to the physicalcontroller. As described herein, the mobile computing device candownload binary configuration data that can be uploaded or installed onthe physical controller. The configuration data can be utilized toconfigure the physical controller.

In some examples, the method 570 can include altering, at the mobilecomputing device, a number of functional settings for the physicalcontroller. In some examples, the mobile computing device can beutilized to alter functional settings of the physical controller. Forexample, the mobile computing device can be utilized to activate and/ordeactivate the physical controller. In another example, the mobilecomputing device can be utilized to activate and/or deactivateparticular features of the physical controller.

FIG. 6 is an example of a computing device 690 for multi-usercommissioning according to one or more embodiments of the presentdisclosure. Computing device 690 can be, for example, a commodityserver, a data center that comprises a plurality of servers, among othertypes of computing devices or embedded system. Computing device 690 canbe utilized in system 102, display 206 and 330, and/or methods 450 and570 to perform the functions previously described herein. For example,computing device 690 can be included in a mobile device such as mobilecomputing device 160 as referenced in FIG. 1.

As shown in FIG. 6, computing device 690 includes a memory 692 and aprocessing resource 694 (e.g., processor) coupled to memory 692. Memory692 can be any type of storage medium that can be accessed by processingresource 694 to perform various examples of the present disclosure. Forexample, memory 692 can be a non-transitory computer readable mediumhaving computer readable instructions (e.g., computer programinstructions) stored thereon that are executable by processing resource694 to perform localizing a fault on a live cable in accordance with oneor more embodiments of the present disclosure.

Memory 692 can be volatile or nonvolatile memory. Memory 692 can also beremovable (e.g., portable) memory, or non-removable (e.g., internal)memory. For example, memory 692 can be random access memory (RAM) (e.g.,dynamic random access memory (DRAM) and/or phase change random accessmemory (PCRAM)), read-only memory (ROM) (e.g., electrically erasableprogrammable read-only memory (EEPROM) and/or compact-disc read-onlymemory (CD-ROM)), flash memory, a laser disc, a digital versatile disc(DVD) or other optical disk storage, and/or a magnetic medium such asmagnetic cassettes, tapes, or disks, among other types of memory.

Further, although memory 692 is illustrated as being located incomputing device 690, embodiments of the present disclosure are not solimited. For example, memory 692 can also be located internal to anothercomputing resource (e.g., enabling computer readable instructions to bedownloaded over the Internet or another wired or wireless connection).

As shown in FIG. 6, computing device 690 can also include a userinterface 696. User interface 696 can include, for example, a display(e.g., a screen). The display can be, for instance, a touch-screen(e.g., the display can include touch-screen capabilities). Userinterface 696 (e.g., the display of user interface 696) can provide(e.g., display and/or present) information to a user of computing device690.

Additionally, computing device 690 can receive information from the userof computing device 690 through an interaction with the user via userinterface 696. For example, computing device 690 (e.g., the display ofuser interface 696) can receive input from the user via user interface696. The user can enter the input into computing device 690 using, forinstance, a mouse and/or keyboard associated with computing device 690,or by touching the display of user interface 696 in embodiments in whichthe display includes touch-screen capabilities (e.g., embodiments inwhich the display is a touch screen).

As used herein, “a” or “a number of” something can refer to one or moresuch things. For example, “a number of resources” can refer to one ormore resources. Additionally, the designator “N”, as used herein,particularly with respect to reference numerals in the drawings,indicates that a number of the particular feature so designated can beincluded with a number of embodiments of the present disclosure.

As described herein, a “module” can include computer readableinstructions that can be executed by a processing resource to perform aparticular function. A module can also include hardware, firmware,and/or logic that can perform a particular function.

As used herein, “logic” is an alternative or additional processingresource to execute the actions and/or functions, described herein,which includes hardware (e.g., various forms of transistor logic,application specific integrated circuits (ASICs)), as opposed tocomputer executable instructions (e.g., software, firmware) stored inmemory and executable by a processing resource.

Although specific embodiments have been illustrated and describedherein, those of ordinary skill in the art will appreciate that anyarrangement calculated to achieve the same techniques can be substitutedfor the specific embodiments shown. This disclosure is intended to coverany and all adaptations or variations of various embodiments of thedisclosure.

It is to be understood that the above description has been made in anillustrative fashion, and not a restrictive one. Combination of theabove embodiments, and other embodiments not specifically describedherein will be apparent to those of skill in the art upon reviewing theabove description.

The scope of the various embodiments of the disclosure includes anyother applications in which the above elements and methods are used.Therefore, the scope of various embodiments of the disclosure should bedetermined with reference to the appended claims, along with the fullrange of equivalents to which such claims are entitled.

In the foregoing Detailed Description, various features are groupedtogether in example embodiments illustrated in the figures for thepurpose of streamlining the disclosure. This method of disclosure is notto be interpreted as reflecting an intention that the embodiments of thedisclosure require more features than are expressly recited in eachclaim.

Rather, as the following claims reflect, inventive subject matter liesin less than all features of a single disclosed embodiment. Thus, thefollowing claims are hereby incorporated into the Detailed Description,with each claim standing on its own as a separate embodiment.

What is claimed:
 1. A system for multi-user commissioning, comprising: amobile computing device comprising computer readable instructions storedthereon that are executable by a processor to: retrieve configurationdata for a physical controller from a remote database; install theconfiguration data on the physical controller; receive data associatedwith a status of the physical controller after the configuration data isinstalled on the physical controller; and synchronize the dataassociated with the status of the physical controller with the remotedatabase.
 2. The system of claim 1, wherein the instructions areexecutable by the processor to receive a notification of a projectassociated with the physical controller.
 3. The system of claim 2,wherein the notification includes a description of the project and alocation of the physical controller.
 4. The system of claim 1, whereinthe configuration data configures a number of settings for functionalityof the physical controller upon being installed on the physicalcontroller.
 5. The system of claim 1, wherein the remote databasereceives an input synchronization from a plurality of additional mobilecomputing devices for the project.
 6. The system of claim 1, wherein thedata associated with a status of the physical controller includesinstallation instructions for the physical controller and checkoutinstructions for the physical controller.
 7. The system of claim 1,wherein the instructions are executable by the processor to record anumber of tests on the physical controller and synchronize results fromthe number of tests with the remote database.
 8. A mobile computingdevice comprising computer readable instructions stored thereon that areexecutable by a processor to: download project instructions for aproject from a remote distributed database; generate a project checklistfor the project based on the project instructions and informationscanned from a device associated with the project; receive selectableinputs corresponding to the project checklist; and synchronize inputsfor the project checklist with the remote distributed database.
 9. Themobile computing device of claim 8, wherein the instructions areexecutable to request configuration data based on information scannedfrom a physical controller.
 10. The mobile computing device of claim 8,wherein the project instructions include a location of the project. 11.The mobile computing device of claim 8, wherein the project checklistincludes a wiring checkout instruction, a sensor calibrationinstruction, and a sequence validation instruction.
 12. The mobilecomputing device of claim 8, wherein the instructions to synchronizeinputs for the project checklist include instructions to synchronizeinputs received from the device associated with the project via aconnection between the device and the mobile computing device.
 13. Amethod for multi-user commissioning, comprising: receiving, at a mobilecomputing device, a notification of a project associated with a physicalcontroller; downloading, at the mobile computing device, projectinstructions for the project from a remote distributed database, whereinthe project instructions includes configuration data for the physicalcontroller; generating, at the mobile computing device, a projectchecklist for the project based on the project instructions for theproject, wherein the project checklist includes instructions to uploadthe configuration data to the physical controller; updating, at themobile computing device, the project checklist to include informationrelating to completed tasks associated with the project, wherein thecompleted tasks include uploading the configuration data to the physicalcontroller; and synchronizing, at the mobile computing device, theproject checklist with the remote distributed database.
 14. The methodof claim 13, comprising displaying, on a display of the mobile computingdevice, the generated project checklist.
 15. The method of claim 14,comprising receiving inputs, at the display of the mobile computingdevice, corresponding to the project checklist upon completion of tasksassociated with the project.
 16. The method of claim 13, comprisingcalibrating the physical controller by uploading the configuration datato the physical controller.
 17. The method of claim 13, wherein updatingthe project checklist includes inputting, at the display, test resultsfor the project.
 18. The method of claim 13, comprising displaying, atthe display of the mobile computing device, an overview of progress forthe project.
 19. The method of claim 13, comprising switching, at thedisplay of the mobile computing device, from the project to a differentproject.
 20. The method of claim 13, comprising altering, at the mobilecomputing device, a number of functional settings for the physicalcontroller.